System for exchanging messages between customer devices and servers

ABSTRACT

Systems ( 1 ) for exchanging messages ( 10 - 13,40 - 55 ) between customer devices ( 2 ) such as customer premises equipment and servers ( 3 ) such as auto configuration servers at several layers comprising a first layer such as a hyper text transfer protocol layer and a second layer such as a simple object access protocol layer are made compliant to web services toolkits by, at the second layer, allowing the customer device ( 2 ) to be a requesting party only and the server ( 3 ) to be a responding party only, for so-called server method applications as well as for so-called customer device method applications. At the second layer, the server ( 3 ) is never a requesting party and the customer device ( 2 ) is never a responding party. As a result, the development of management appliances no longer needs to be done manually and the system ( 1 ) according to the invention can be used in combination with firewalls.

The invention relates to a system for exchanging messages between acustomer device and a server at several layers comprising a first layerand a second layer, the customer device being a requesting party at thefirst layer and the server being a responding party at the first layer,the customer device being a requesting party at the second layer and theserver being a responding party at the second layer, which second layeris higher than the first layer.

Examples of such a system are environments comprising a private part anda public part coupled to each other via a network. The customer devicefor example forms part of the private part, and the server for exampleforms part of the public part. In the system, the overall requirement isto be fullfilled that the server must be able to read (find out) andupdate the settings of the customer device.

A prior art system is of common general knowledge and for example incorrespondance with the WT-87 management protocol, also known as TR-69.At the first lower layer, the customer device always is a requestingparty or initiating party and the server always is a responding party orreacting party. At the second higher layer, the customer device might bea requesting party or a responding party respectively and the servermight be a responding party or a requesting party respectively. In otherwords, at the first lower layer, request messages flow from the customerdevice to the server, and response messages flow from the server to thecustomer device. At the second higher layer, request messages flow fromthe customer device to the server or vice versa, and response messagesflow from the server to the customer device or vice versa.

For so-called server method applications, the customer device can callon the server. In this case, the request message at the first layer andthe request message at the second layer usually form part of one and thesame packet, cell or frame, and the response message at the first layerand the response message at the second layer usually form part of oneand the same packet, cell or frame. Thereby, each packet, cell or frameis processed per layer in an individual way.

For so-called customer device method applications, the server can callon the customer device. In this case, the request message at the firstlayer and the request message at the second layer usually do not formpart of one and the same packet, cell or frame, and the response messageat the first layer and the response message at the second layer usuallydo not form part of one and the same packet, cell or frame. The reasonfor this is that, at the first layer, only the customer device cantransmit request messages, and only the server can transmit responsemessages. Therefore, an alternative way had to be found to make itpossible to let the server call on the customer device. According tothis alternative way, the customer device transmits a packet, cell orframe comprising a request message at the first layer and not comprisingany second layer message to the server. The server detects a presence ofthis request message at the first layer and an absence of any message atthe second layer, and knows that the customer device is offering theserver a possibility of sending a request message at the second layer tothe customer device. Thereto, the server transmits a packet, cell orframe comprising a response message at the first layer and a requestmessage at the second layer to the customer device. The customer devicedetects these messages in the packet, cell or frame and reacts bytransmitting a packet, cell or frame comprising a request message at thefirst layer and a response message at the second layer to the serveretc. So, in this case, the request message at the first layer and theresponse message at the second layer usually form part of one and thesame packet, cell or frame, and the response messages at the first layerand the request message at the second layer usually form part of one andthe same packet, cell or frame. Thereby, again, each packet, cell orframe is processed per layer in an individual way.

The known system is disadvantageous, inter alia, owing to the fact thatit is not compliant with for example web services supporting toolkits. Apacket, cell or frame comprising a request message at the first layerand not comprising any second layer message contravenes the web servicessupporting toolkits. As a result, the development of managementappliances needs to be done manually. The known system is furtherdisadvantageous, inter alia, owing to the fact that it does not allowfirewalls to be present between the customer device and the server,which firewalls forbid requests coming from the server in both lower andhigher layer of the packets.

It is an object of the invention, inter alia, to provide a system asdefined in the preamble which is compliant with at least some webservices supporting toolkits.

The system according to the invention is characterised in that theserver is not a requesting party at the second layer and the customerdevice is not a responding party at the second layer.

By deleting the possibility of the server being a requesting party atthe second layer and the customer device being a responding party at thesecond layer, in other words by making it impossible that the serverplays the requesting party at the second layer and the customer deviceplays the responding party at the second layer, the system according tothe invention has become compliant with one or more web servicessupporting toolkits. The reason for this is that the symmetry of themessages has been restored.

The system according to the invention is firstly advantageous in thatthe development of management appliances no longer needs to be donemanually and is secondly advantageous in that the system according tothe invention can be used in combination with firewalls. Such firewallsallow request messages to flow in one direction only. Therefore, theprior art system could not be combined with a firewall, which is quiterisky these days.

An embodiment of the system according to the invention is characterisedin that the customer device is a customer premises equipment and theserver is an auto configuration server.

The system according to the invention preferably comprises a customerpremises equipment and an auto configuration server, without excludingother and further equipment and other and further servers.

An embodiment of the system according to the invention is characterisedin that the first layer is a hyper text transfer protocol layer and thesecond layer is a simple object access protocol layer.

The system according to the invention preferably exchanges messages at ahyper text transfer protocol layer and a simple object access protocollayer, without excluding other and further layers.

An embodiment of the system according to the invention is characterisedin that a first message signal comprises a request message at the firstlayer and a GetCPEMethodType{} message at the second layer, a secondmessage signal comprises a response message at the first layer and aMethod1 message at the second layer, a third message signal comprises arequest message at the first layer and a GetMethod1Arguments{id} messageat the second layer, a fourth message signal comprises a responsemessage at the first layer and a Method1Arguments message at the secondlayer, and a fifth message signal comprises a request message at thefirst layer and a SetMethod1Result{id,result} message at the secondlayer.

In this case, the overhead and the complexity have increased, owing tothe fact that five message signals need to be exchanged according to theinvention, compared to only three message signals needing to beexchanged in accordance with the prior art. The five message signals arenecessary for performing a session with one or more so-called remoteprocedure calls. According to the prior art, only three message signalswere necessary for performing a session with one or more so-calledremote procedure calls.

An embodiment of the system according to the invention is characterisedin that a sixth message signal comprises a response message at the firstlayer and a Method2 message at the second layer.

In this case, the sixth message signal is used for starting the nextsession with one or more remote procedure calls.

The invention also relates to a method for exchanging messages between acustomer device and a server at several layers comprising a first layerand a second layer, the method comprising the steps of

-   at the first layer, transmitting a request message from the customer    device to the server and transmitting a response message from the    server to the customer device,-   at the second layer, transmitting a request message from the    customer device to the server and transmitting a response message    from the server to the customer device,    which second layer is higher than the first layer, characterized in    that the method comprises the step of-   at the second layer, not transmitting a request message from the    server to the customer device and not transmitting a response    message from the customer device to the server.

Instead of comprising the step of, at the second layer, not transmittinga request message from the server to the customer device and nottransmitting a response message from the customer device to the server,alternatively, the method according to the invention might becharacterised in that the method does not comprise the step of, at thesecond layer, transmitting a request message from the server to thecustomer device and transmitting a response message from the customerdevice to the server.

The invention yet also relates to a processor program product forexchanging messages between a customer device and a server at severallayers comprising a first layer and a second layer, the processorprogram product comprising the functions of

-   at the first layer, transmitting a request message from the customer    device to the server and transmitting a response message from the    server to the customer device,-   at the second layer, transmitting a request message from the    customer device to the server and transmitting a response message    from the server to the customer device,    which second layer is higher than the first layer, characterized in    that the processor program product comprises the function of-   at the second layer, not transmitting a request message from the    server to the customer device and not transmitting a response    message from the customer device to the server.

Instead of comprising the function of, at the second layer, nottransmitting a request message from the server to the customer deviceand not transmitting a response message from the customer device to theserver, alternatively, the processor program product according to theinvention might be characterised in that the processor program productdoes not comprise the function of, at the second layer, transmitting arequest message from the server to the customer device and transmittinga response message from the customer device to the server.

The invention also relates to a customer device for exchanging messageswith a server at several layers comprising a first layer and a secondlayer, the customer device comprising

-   a customer device transmitter for, at the first layer, transmittting    a request message to the server and, at the second layer,    transmitting a request message to the server, and-   a customer device receiver for, at the first layer, receiving a    response message from the server and, at the second layer, receiving    a response message from the server,    which second layer is higher than the first layer, characterized in    that the customer device transmitter is arranged for, at the second    layer, not transmitting a response message to the server and the    customer device receiver is arranged for, at the second layer, not    receiving a request message from the server.

Instead of the customer device transmitter being arranged for, at thesecond layer, not transmitting a response message to the server and thecustomer device receiver being arranged for, at the second layer, notreceiving a request message from the server, alternatively, thecustormer device according to the invention might be characterised inthat the customer device transmitter is not arranged for, at the secondlayer, transmitting a response message to the server and the customerdevice receiver is not arranged for, at the second layer, receiving arequest message from the server.

The invention yet also relates to a server for exchanging messages witha customer device at several layers comprising a first layer and asecond layer, the server comprising

-   a server receiver for, at the first layer, receiving a request    message from the customer device and, at the second layer, receiving    a request message from the customer device, and-   a server transmitter for, at the first layer, transmittting a    response message to the customer device and, at the second layer,    transmitting a response message to the customer device,    which second layer is higher than the first layer, characterized in    that the server receiver is arranged for, at the second layer, not    receiving a response message from the customer device and the server    transmitter is arranged for, at the second layer, not transmitting a    request message to the customer device.

Instead of the server receiver being arranged for, at the second layer,not receiving a response message from the customer device and the servertransmitter being arranged for, at the second layer, not transmitting arequest message to the customer device, alternatively the server mightbe characterised in that the server receiver is not arranged for, at thesecond layer, receiving a response message from the customer device andthe server transmitter is not arranged for, at the second layer,transmitting a request message to the customer device.

And the invention relates to a message signal to be exchanged between acustomer device and a server at several layers comprising a first layerand a second layer, characterised in that the message signal comprisesat least one of a GetCPEMethodType{} message, a Method1 message, aGetMethod1Arguments{id} message, a Method1Arguments message, aSetMethod1Result{id,result} message and a response Method2 message.

Embodiments of the method according to the invention and of theprocessor program product according to the invention and of the customerdevice according to the invention and of the server according to theinvention and of the message signal according to the inventioncorrespond with the embodiments of the system according to theinvention.

The invention is based upon an insight, inter alia, that web servicestoolkits require symmetrical message signals, and is based upon a basicidea, inter alia, that the server should never be a requesting party atthe second layer and the customer device should never be a respondingparty at the second layer.

The invention solves the problem, inter alia, to provide a system asdefined in the preamble which is compliant with at least some webservices supporting toolkits, and is advantageous, inter alia, in thatthe development of management appliances no longer needs to be donemanually and in that the system according to the invention can be usedin combination with firewalls.

These and other aspects of the invention will be apparent from andelucidated with reference to the embodiments(s) described hereinafter.

FIG. 1 shows a message chart for a prior art system comprising a priorart customer device and a prior art server;

FIG. 2 shows a message chart for a system according to the inventioncomprising a customer device according to the invention and a serveraccording to the invention; and

FIG. 3 shows diagrammatically a system according to the inventioncomprising a customer device according to the invention and a serveraccording to the invention.

In FIG. 1 (prior art) showing a message chart for a prior art system 100comprising a prior art customer device 200 and a prior art server 300,the blocks 10-13 are related to the so-called server methodapplications, whereby the customer device 200 can call on the server300. The blocks 20-31 are related to the so-called customer devicemethod applications, whereby the server 300 can call on the customerdevice 200. These blocks have the following meaning:

Block 10: Request message at a first layer.

Block 11: Request message at a second layer.

This represents a server method e.g. a TR69 Inform message, a requestthat informs the server of activity and starts a session in which otherrequests in both directions can be done.

Block 12: Response message at the first layer.

Block 13: Response message at the second layer

This represents a server method response e.g. a TR69 InformResponsemessage, a response that answers the inform.

Block 20: Request message at the first layer.

Block 21: Missing request message at the second layer.

Block 22: Response message at the first layer.

Block 23: Request message at the second layer.

This represents a first customer device method e.g. a TR69setParameterValues(parameter struct1), a request that asks the customerdevice to set its parameter values according to the values of the passedstruct1.

Block 24: Request message at the first layer.

Block 25: Response message at the second layer.

This represents the corresponding customer device method response e.g. aTR69 setParameterValuesResponse, a response that informs the server thatthe request was executed.

Block 26: Response message at the first layer.

Block 27: Request message at the second layer.

This represents a second customer device method e.g. a TR69setParameterValues(parameter struct2), a request that asks the customerdevice to set its parameter values according to the values of the passedstruct1.

Block 28: Request message at the first layer.

Block 29: Response message at the second layer.

This represents the corresponding customer device method response e.g. aTR69 setParameterValuesResponse, a response that informs the server thatthe request was executed.

Block 30: Response message at the first layer.

Block 31: Missing response message at the second layer.

With respect to the so-called server method applications, whereby thecustomer device 200 can call on the server 300, the request message 10at the first layer and the request message 11 at the second layerusually form part of one and the same message signal 10,11 transportedby a packet, cell or frame, and the response message 12 at the firstlayer and the response message 13 at the second layer usually form partof one and the same message signal 12,13 transported by a packet, cellor frame.

With respect to the so-called customer device method applications,whereby the server 300 can call on the customer device 200, the requestmessage 20,24,28 at the first layer and the request message 23,27 at thesecond layer usually do not form part of one and the same message signaltransported by a packet, cell or frame, and the response message22,26,30 at the first layer and the response message 25,29 at the secondlayer usually do not form part of one and the same message signaltransported by a packet, cell or frame. The reason for this is that, atthe first layer, only the customer device 200 can transmit requestmessages, and only the server 300 can transmit response messages.Therefore, an alternative way had to be found to make it possible to letthe server 300 call on the customer device 200. According to thisalternative way, the customer device 200 transmits a packet, cell orframe comprising a request message 20 at the first layer and notcomprising any second layer message 21 to the server 300. The server 300detects a presence of this request message 20 at the first layer and anabsence of any message 21 at the second layer, and knows that thecustomer device 200 is offering the server 300 a possibility of sendinga request message 23 at the second layer to the customer device 200.Thereto, the server 300 transmits a packet, cell or frame comprising aresponse message 22 at the first layer and a request message 23 at thesecond layer to the customer device 200. The customer device 200 detectsthese messages in the packet, cell or frame and reacts by transmitting apacket, cell or frame comprising a request message 24 at the first layerand a response message 25 at the second layer to the server 300 etc. So,in this case, the request message at the first layer and the responsemessage at the second layer usually form part of one and the samepacket, cell or frame, and the response messages at the first layer andthe request message at the second layer usually form part of one and thesame packet, cell or frame.

The known system 100 is disadvantageous, inter alia, owing to the factthat it is not compliant with for example web services supportingtoolkits such as for example the WS (Web Services) Basic Profile 1.0. Apacket, cell or frame comprising a request message at the first layerand not comprising any second layer message contravenes the web servicessupporting toolkits. The invention as shown in FIGS. 2 and 3 solves thisproblem, whereby, for example, the customer device 2 is a customerpremises equipment and the server 3 is an auto configuration server,without excluding other and further equipment and other and furtherservers, and, for example, the first layer is a hyper text transferprotocol layer and the second layer is a simple object access protocollayer, without excluding other and further layers.

In FIG. 2 (invention) showing a message chart for a system 1 accordingto the invention comprising a customer device 2 according to theinvention and a server 3 according to the invention, the blocks 10-13are related to the so-called server method applications, whereby thecustomer device 2 can call on the server 3. The blocks 40-55 are relatedto the so-called customer device method applications, whereby the server3 can call on the customer device 2. These blocks have the followingmeaning:

Block 10: Request message at a first layer.

Block 11: Request message at a second layer.

This represents a server method e.g. a TR69 Inform message, a requestthat informs the server of activity and starts a session in which otherrequests in both directions can be done.

Block 12: Response message at the first layer.

Block 13: Response message at the second layer.

This represents a server method response e.g. a TR69 InformResponsemessage, a response that answers the inform.

Block 40: Request message at the first layer.

Block 41: Request message at the second layer.

This represents a server method asking which task the customer deviceneeds to perform: getServerMethodType.

Block 42: Response message at the first layer.

Block 43: Response message at the second layer.

This represents a server method response, answering which task thecustomer device needs to perform e.g. setParameterValues.

Block 44: Request message at the first layer.

Block 45: Request message at the second layer. This represents a servermethod asking the arguments with which the task needs to be performede.g. getSetParameterValuesArguments.

Block 46: Response message at the first layer.

Block 47: Response message at the second layer.

This represents a server method reponse answering which parameters needto be set e.g. parameterstruct1 which is a list of name,value pairs.

Block 48: Request message at the first layer.

Block 49: Request message at the second layer.

This represents a server method that is setting the result of executionon the server e.g. setSetParameterValuesResult is setting the result ofthe execution, the passed value could be e.g. “success” or “fault”.

Block 50: Response message at the first layer.

Block 51: Response message at the second layer.

This represents the corresponding server method response. This responsecan contain the method name of a second operation that the server wantsto be executed on the customer device, or it can contain no data if nomore operations need to be executed. In the second case, it is justallowing the customer device to know that the server has correctlyprocessed the server method.

Block 52: Request message at the first layer.

Block 53: Request message at the second layer.

This represents the next server method in the case a second operationwas passed in block 51. In that case, the rest of the message flow isthe same as from block 45.

Block 54: Response message at the first layer.

Block 55: Response message at the second layer.

With respect to the so-called server method applications, whereby thecustomer device 2 can call on the server 3, the request message 10 atthe first layer and the request message 11 at the second layer usuallyform part of one and the same message signal 10,11 transported by apacket, cell or frame, and the response message 12 at the first layerand the response message 13 at the second layer usually form part of oneand the same message signal 12,13 transported by a packet, cell orframe. So, for the server method applications, there are no differencesbetween the prior art and the invention.

With respect to the so-called customer device method applications,whereby the server 3 can call on the customer device 2, there are manydifferences between the prior art and the invention, general differencesand particular differences.

About the general differences, according to the invention, a requestmessage at the first layer and a response message at the second layerare no longer combined in one and the same message signal, and aresponse message at the first layer and a request message at the secondlayer are no longer combined in one and the same message signal.

About the more particular differences, a first message signal 40,41comprises for example a request message 40 at the first layer and aGetCPEMethodType{} message 41 at the second layer, a second messagesignal 42,43 comprises for example a response message 42 at the firstlayer and a Method1 message 43 at the second layer, a third messagesignal 44,45 comprises for example a request message 44 at the firstlayer and a GetMethod1Arguments{id} message 45 at the second layer, afourth message signal 46,47 comprises for example a response message 46at the first layer and a Method1Arguments message 47 at the secondlayer, a fifth message signal 48,49 comprises for example a requestmessage 48 at the first layer and a SetMethod1Result{id,result} message49 at the second layer, a sixth message signal 50,51 comprises forexample a response message 50 at the first layer and a Method2 message51 at the second layer, a seventh message signal 52,53 comprises forexample a request message 52 at the first layer and aGetMethod2Arguments{id} message 53 at the second layer and an eighthmessage signal 54,55 comprises for example a response message 54 at thefirst layer and a Method2Arguments message 55 at the second layer.

The GetCPEMethodType{} message 41 at the second layer is a requestmessage at the second layer, the Method1 message 43 at the second layeris a response message at the second layer, the GetMethod1Arguments{id}message 45 at the second layer is a request message at the second layer,the Method1Arguments message 47 at the second layer is a responsemessage at the second layer, and the SetMethod1Result{id,result} message49 at the second layer is a request message at the second layer. So, asa result, according to the invention a request message at the firstlayer is always combined with a request message at the second layer anda response message at the first layer is always combined with a responsemessage at the second layer. But the second layer messages are suchthat, after a session comprising one or more remote procedure calls eachcomprising one or more exchanged message signals, the final state of thecustomer device 2 and of the server 3 is the same as if the server 3would have had the possibility to do a request and as if the customerdevice would have had the possibility to respond to that request.

In other words, the customer device method applications or CPE methodapplications are mapped to the web services by splitting each CPE remoteprocedure call method into three web services calls:

-   I) get<CPEMethod>Type{}, returning a <CPEMethod>Type message    containing type and id.-   II) get<CPEMethod>Argument{id}, where <CPEmethod> depends on the    return type of the previous call, returning a <CPEMethod>Argument    message.

After the customer device 2 has executed the method locally it calls athird web service call:

-   III) set<CPEMethod>Response{id,methodResult}, which passes a    methodResult indicating the result of the CPE Method (success or    fault). This method returns the next <CPEMethod>Type if the server 3    needs to call another CPE method, or not (if not, a “null” is    returned, which is completely different from an empty hyper text    transfer protocol request: the “null” is represented by bits    defining this “null”, with a web services toolkit being written to    recognize these bits automatically).

The CPE method context can be kept by using a method id which is sharedover the three remote procedure calls. The system 1 according to theinvention has many advantages:

-   A) Rapid application development for both server and customer device    developers, because web services toolkits become available.-   B) Use of a WSDL (Web Services Description Language) minimizes    interoperability issues between the customer device and the server.-   C) web services specific security packages become available for    securing the customer device-server communication e.g. WSS4J (web    services security for java).-   D) UDDI (Universal Discovery Description & Integration) can be used    as a registry: the server publishes its service and the customer    device can look it up, so no need to preconfigure the customer    device where the server is located.-   E) Deployability increases e.g. new server software releases can be    deployed remotely through the firewalls.-   F) web services is growing and evolving very rapidly in the IT    world. A customer device management protocol that is based on web    services can profit from future extensions.

In FIG. 3 (invention) a system 1 according to the invention is showndiagrammatically comprising a customer device 2 according to theinvention and a server 3 according to the invention. The customer device2 according to the invention comprises a customer device processorsystem 60 coupled to a customer device transmitter 61 and to a customerdevice receiver 63. The customer device transmitter 61 and the customerdevice receiver 63 are further coupled to a customer device interface 62which is further coupled to a coupling 4 such as for example a wired(analog, integrated services digital network, digital subscriber line)electrical or optical coupling or a wireless (GSM, UMTS) coupling. Thecustomer device processor system 60 is further coupled to a customerdevice man machine interface 64.

The server 3 according to the invention comprises a server processorsystem 70 coupled to a server transmitter 71 and to a server receiver73. The server transmitter 71 and the server receiver 73 are furthercoupled to a server interface 72 which is coupled to the coupling 4. Inpractice, the server 3 will be coupled to many customer devices 2 viaone or more switches, multiplexers, bridges, forwarders, routers etc.all not shown.

In the system 1 according to the invention, the overall requirement isto be fullfilled that the server 3 according to the invention must beable to read (find out) and update the settings of the customer device 2according to the invention.

According to the invention, the customer device transmitter 61 isarranged for, at the second layer, not transmitting a response message25 to the server 3 and the customer device receiver 63 is arranged for,at the second layer, not receiving a request message 23 from the server3. In other words, the customer device processor system 60 is designedto process a combination of a request message at the first layer and arequest message at the second layer and is designed to process acombination of a response message at the first layer and a responsemessage at the second layer. The customer device processor system 60 isdisabled to process a combination of a request message at the firstlayer and a response message at the second layer and is disabled toprocess a combination of a response message at the first layer and arequest message at the second layer.

According to the invention, the server receiver 73 is arranged for, atthe second layer, not receiving a response message 25 from the customerdevice 2 and the server transmitter 71 is arranged for, at the secondlayer, not transmitting a request message 23 to the customer device 2.In other words, the server processor system 70 is designed to process acombination of a request message at the first layer and a requestmessage at the second layer and is designed to process a combination ofa response message at the first layer and a response message at thesecond layer. The server processor system 70 is disabled to process acombination of a request message at the first layer and a responsemessage at the second layer and is disabled to process a combination ofa response message at the first layer and a request message at thesecond layer.

The expression “for” in for example “for exchanging”, “for transmitting”and “for receiving” etc. does not exclude that other functions areperformed as well, simultaneously or not. The expressions “X coupled toY” and “a coupling between X and Y” and “coupling/couples X and Y” etc.do not exclude that an element Z is in between X and Y. The expressions“P comprises Q” and “P comprising Q” etc. do not exclude that an elementR is comprised/included as well. The terms “a” and “an” do not excludethe possible presence of one or more pluralities.

The steps/functions of for example “transmitting” and “not transmitting”etc. do not exclude further steps/functions, such as for example, interalia, the steps/functions described in the specification.

1. System (1) for exchanging messages (10-13,40-55) between a customerdevice (2) and a server (3) at several layers comprising a first layerand a second layer, the customer device (2) being a requesting party atthe first layer and the server (3) being a responding party at the firstlayer, the customer device (2) being a requesting party at the secondlayer and the server (3) being a responding party at the second layer,which second layer is higher than the first layer, characterized in thatthe server (3) is not a requesting party at the second layer and thecustomer device (2) is not a responding party at the second layer. 2.System (1) as defined in claim 1, characterised in that the customerdevice (2) is a customer premises equipment and the server (3) is anauto configuration server.
 3. System (1) as defined in claim 1,characterised in that the first layer is a hyper text transfer protocollayer and the second layer is a simple object access protocol layer. 4.System (1) as defined in claim 1, characterised in that a first messagesignal (40,41) comprises a request message (40) at the first layer and aGetCPEMethodType{} message (41) at the second layer, a second messagesignal (42,43) comprises a response message (42) at the first layer anda Method1 message (43) at the second layer, a third message signal(44,45) comprises a request message (44) at the first layer and aGetMethod1Arguments{id} message (45) at the second layer, a fourthmessage signal (46,47) comprises a response message (46) at the firstlayer and a Method1Arguments message (47) at the second layer, and afifth message signal (48,49) comprises a request message (48) at thefirst layer and a SetMethod1Result{id,result} message (49) at the secondlayer.
 5. System (1) as defined in claim 4, characterised in that asixth message signal (50,51) comprises a response message (50) at thefirst layer and a Method2 message (51) at the second layer.
 6. Methodfor exchanging messages (10-13,40-55) between a customer device (2) anda server (3) at several layers comprising a first layer and a secondlayer, the method comprising the steps of at the first layer,transmitting a request message (40) from the customer device (2) to theserver (3) and transmitting a response message (42) from the server (3)to the customer device (2), at the second layer, transmitting a requestmessage (41) from the customer device (2) to the server (3) andtransmitting a response message (43) from the server (3) to the customerdevice (2), which second layer is higher than the first layer,characterized in that the method comprises the step of at the secondlayer, not transmitting a request message (23) from the server (3) tothe customer device (2) and not transmitting a response message (25)from the customer device (2) to the server (3).
 7. Processor programproduct for exchanging messages (10-13,40-55) between a customer device(2) and a server (3) at several layers comprising a first layer and asecond layer, the processor program product comprising the functions ofat the first layer, transmitting a request message (40) from thecustomer device (2) to the server (3) and transmitting a responsemessage (42) from the server (3) to the customer device (2), at thesecond layer, transmitting a request message (41) from the customerdevice (2) to the server (3) and transmitting a response message (43)from the server (3) to the customer device (2), which second layer ishigher than the first layer, characterized in that the processor programproduct comprises the function of at the second layer, not transmittinga request message (23) from the server (3) to the customer device (2)and not transmitting a response message (25) from the customer device(2) to the server (3).
 8. Customer device (2) for exchanging messageswith a server (3) at several layers comprising a first layer and asecond layer, the customer device (2) comprising a customer devicetransmitter (61) for, at the first layer, transmittting a requestmessage (40) to the server (3) and, at the second layer, transmitting arequest message (41) to the server (3), and a customer device receiver(63) for, at the first layer, receiving a response message (42) from theserver (3) and, at the second layer, receiving a response message (43)from the server (3), which second layer is higher than the first layer,characterized in that the customer device transmitter (61) is arrangedfor, at the second layer, not transmitting a response message (25) tothe server (3) and the customer device receiver (63) is arranged for, atthe second layer, not receiving a request message (23) from the server(3).
 9. Server (3) for exchanging messages with a customer device (2) atseveral layers comprising a first layer and a second layer, the server(3) comprising a server receiver (73) for, at the first layer, receivinga request message (40) from the customer device (2) and, at the secondlayer, receiving a request message (41) from the customer device (2),and a server transmitter (71) for, at the first layer, transmittting aresponse message (42) to the customer device (2) and, at the secondlayer, transmitting a response message (43) to the customer device (2),which second layer is higher than the first layer, characterized in thatthe server receiver (73) is arranged for, at the second layer, notreceiving a response message (25) from the customer device (2) and theserver transmitter (71) is arranged for, at the second layer, nottransmitting a request message (23) to the customer device (2). 10.Message signal (40-41,42-43,44-45,46-47,48-49,50-51) to be exchangedbetween a customer device (2) and a server (3) at several layerscomprising a first layer and a second layer, characterised in that themessage signal comprises at least one of a GetCPEMethodType{} message(41), a Method1 message (43), a GetMethod1Arguments{id} message (45), aMethod1Arguments message (47), a SetMethod1Result{id,result} message(49) and a response Method2 message (51).